Apparatus, system and method of setting up an application service platform (asp) peer to peer (p2p) group

ABSTRACT

Some demonstrative embodiments include apparatuses, systems and/or methods of setting up an Application Service Platform (ASP) Peer-to-Peer (P2P) persistent group. For example, an apparatus may include a first ASP to communicate with a second ASP to setup one or more ASP-P2P groups over a wireless communication link, the first ASP is to form each ASP-P2P group only as an ASP-P2P persistent group extendable over a plurality of distinct sessions, the first ASP is to store credentials of the ASP-P2P persistent group for use during the sessions.

CROSS REFERENCE

This application is a Continuation Application of U.S. patentapplication Ser. No. 14/028,742, filed on Sep. 17, 2013, which in turnclaims the benefit of and priority from U.S. Provisional PatentApplication No. 61/820,996 entitled “Techniques of Invoking PersistentP2P group For Application Service Platform (ASP)”, filed on May 8, 2013,the entire disclosures of which are incorporated herein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to an apparatus, systemand method of setting up an Application Service Platform (ASP)Peer-to-Peer (P2P) group.

BACKGROUND

A first wireless communication device may be capable of providing one ormore services to a second wireless communication device. For example,the first wireless communication device may provide printing services,display services, Internet access services, and/or any other service tothe second wireless communication device.

Wireless Fidelity (Wi-Fi) Direct technology provides a Peer-to-Peer(P2P) connectivity to connect between the first and second devices,e.g., to share, show, print, and/or synchronize content.

The Wi-Fi Direct technology provides link-layer connectivity, which maynot support interoperability between services and/or applications frommultiple, e.g., different, vendors. As a result, users may experienceinconsistency when using a service from a remote device, e.g., due tothe lack of interoperability between a device providing services and adevice running applications and/or a complexity of the P2P topology.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a sequence diagram of operations between a first wirelesscommunication device and a second wireless communication device, inaccordance with some demonstrative embodiments.

FIG. 3 is a flow chart illustration of a method of setting up anApplication Service Platform (ASP) Peer-to-Peer (P2P) group, inaccordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a product of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment”, “an embodiment”, “demonstrativeembodiment”, “various embodiments” etc., indicate that the embodiment(s)so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a Wireless Video Area Network (WVAN),a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal AreaNetwork (PAN), a Wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Wireless-Gigabit-Alliance (WGA)specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.1, April 2011, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11 task group ac (TGac) (“IEEE802.11-09/0308r12—TGac ChannelModel Addendum Document”); IEEE 802.11 task group ad (TGad) (IEEEP802.11ad-2012, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 3: Enhancements for Very High Throughput in the60 GHz Band, 28 Dec., 2012)) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWirelessHD™ specifications and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWiFi Alliance (WFA) Peer-to-Peer (P2P) specifications (WiFi P2Ptechnical specification, version 1.3, 2012) and/or future versionsand/or derivatives thereof, devices and/or networks operating inaccordance with existing Wireless Serial Bus (WSB) specifications and/orfuture versions and/or derivatives thereof units and/or devices whichare part of the above networks, and the like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-DivisionMultiple Access (TDMA), Extended TDMA (E-TDMA), General Packet RadioService (GPRS), extended GPRS, Code-Division Multiple Access (CDMA),Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrierCDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT),Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™,Ultra-Wideband (UWB), Global System for Mobile communication (GSM), 2G,2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, LongTerm Evolution (LTE), LTE advanced, Enhanced Data rates for GSMEvolution (EDGE), or the like. Other embodiments may be used in variousother devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a wirelesscommunication signal includes transmitting the wireless communicationsignal and/or receiving the wireless communication signal. For example,a wireless communication unit, which is capable of communicating awireless communication signal, may include a wireless transmitter totransmit the wireless communication signal to at least one otherwireless communication unit, and/or a wireless communication receiver toreceive the wireless communication signal from at least one otherwireless communication unit.

Some demonstrative embodiments may be used in conjunction with a WLAN.Other embodiments may be used in conjunction with any other suitablewireless communication network, for example, a wireless area network, a“piconet”, a WPAN, a WVAN and the like.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmWave)frequency band), e.g., a frequency band within the frequency band ofbetween 20 Ghz and 300 GHZ, a WLAN frequency band, a WPAN frequencyband, a frequency band according to the WGA specification, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The term “station” (STA), as used herein, may include any logical entitythat is a singly addressable instance of a medium access control (MAC)and a physical layer (PHY) interface to a wireless medium (WM).

The phrase “access point” (AP), as used herein, may include an entitythat contains one station (STA) and provides access to distributionservices, via the WM for associated STAs.

The phrase “non-access-point (non-AP) station (STA)”, as used herein,may relate to a STA that is not contained within an AP.

The phrase “peer to peer (PTP or P2P) communication”, as used herein,may relate to device-to-device communication over a wireless link(“peer-to-peer link”) between a pair of devices. The P2P communicationmay include, for example, wireless communication over a direct linkwithin a QoS basic service set (BSS), a tunneled direct-link setup(TDLS) link, a STA-to-STA communication in an independent basic serviceset (IBSS), or the like.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100, in accordance with some demonstrativeembodiments.

As shown in FIG. 1, in some demonstrative embodiments system 100 mayinclude a wireless communication network including one or more wirelesscommunication devices, e.g., wireless communication devices 120 and/or140, capable of communicating content, data, information and/or signalsover a wireless communication medium (WM) 103, for example, a radiochannel, an IR channel, an RF channel, a Wireless Fidelity (WiFi)channel, and the like. One or more elements of system 100 may optionallybe capable of communicating over any suitable wired communication links.

In some demonstrative embodiments, wireless communication devices 120and/or 140 may include, for example, a PC, a desktop computer, a mobilecomputer, a laptop computer, a notebook computer, a tablet computer, anUltrabook™ computer, a server computer, a handheld computer, a handhelddevice, a PDA device, a handheld PDA device, an on-board device, anoff-board device, a hybrid device (e.g., combining cellular phonefunctionalities with PDA device functionalities), a consumer device, avehicular device, a non-vehicular device, a mobile or portable device, anon-mobile or non-portable device, a mobile phone, a cellular telephone,a PCS device, a PDA device which incorporates a wireless communicationdevice, a mobile or portable GPS device, a DVB device, a relativelysmall computing device, a non-desktop computer, a “Carry Small LiveLarge” (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC(UMPC), a Mobile Internet Device (MID), an “Origami” device or computingdevice, a device that supports Dynamically Composable Computing (DCC), acontext-aware device, a video device, an audio device, an A/V device, aSet-Top-Box (STB), a Blu-ray disc (BD) player, a BD recorder, a DigitalVideo Disc (DVD) player, a High Definition (HD) DVD player, a DVDrecorder, a HD DVD recorder, a Personal Video Recorder (PVR), abroadcast HD receiver, a video source, an audio source, a video sink, anaudio sink, a stereo tuner, a broadcast radio receiver, a flat paneldisplay, a Personal Media Player (PMP), a digital video camera (DVC), adigital audio player, a speaker, an audio receiver, an audio amplifier,a gaming device, a data source, a data sink, a Digital Still camera(DSC), a media player, a Smartphone, a television, a music player, orthe like.

In some demonstrative embodiments, wireless communication devices 120and/or 140 may include wireless communication units 112 and/or 142,respectively, to perform wireless communication between wirelesscommunication devices 120 and/or 140 and/or with one or more otherwireless communication devices, e.g., as described below.

In some demonstrative embodiments, wireless communication devices 120and/or 140 may also include, for example, one or more of a processor191, an input unit 192, an output unit 193, a memory unit 194, and astorage unit 195. Wireless communication devices 120 and/or 140 mayoptionally include other hardware components and/or software components.In some demonstrative embodiments, some or all of the components of oneor more of wireless communication devices 120 and/or 140 may be enclosedin a common housing or packaging, and may be interconnected or operablyassociated using one or more wired or wireless links. In otherembodiments, components of one or more of wireless communication devices120 and/or 140 may be distributed among multiple or separate devices.

Processor 191 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of wireless communicationdevices 120 and/or 140 and/or of one or more applications.

Input unit 192 includes, for example, a keyboard, a keypad, a mouse, atouch-screen, a touch-pad, a track-ball, a stylus, a microphone, orother suitable pointing device or input device. Output unit 193includes, for example, a monitor, a screen, a touch-screen, a flat paneldisplay, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display(LCD) display unit, a plasma display unit, one or more audio speakers orearphones, or other suitable output devices.

Memory unit 194 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 195 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 194 and/or storage unit 195,for example, may store data processed by wireless communication devices120 and/or 140.

In some demonstrative embodiments, wireless communication units 112and/or 142 may include, or may be associated with, one or more antennas107 and/or 147, respectively. Antennas 107 and/or 147 may include anytype of antennas suitable for transmitting and/or receiving wirelesscommunication signals, blocks, frames, transmission streams, packets,messages and/or data. For example, antennas 107 and/or 147 may includeany suitable configuration, structure and/or arrangement of one or moreantenna elements, components, units, assemblies and/or arrays. Antennas107 and/or 147 may include, for example, antennas suitable fordirectional communication, e.g., using beamforming techniques. Forexample, antennas 107 and/or 147 may include a phased array antenna, asingle element antenna, a set of switched beam antennas, and/or thelike. In some embodiments, antennas 107 and/or 147 may implementtransmit and receive functionalities using separate transmit and receiveantenna elements. In some embodiments, antennas 107 and/or 147 mayimplement transmit and receive functionalities using common and/orintegrated transmit/receive elements.

In some demonstrative embodiments, wireless communication units 112and/or 142 include, for example, one or more radios 114, e.g., includingone or more wireless transmitters, receivers and/or transceivers able tosend and/or receive wireless communication signals, RF signals, frames,blocks, transmission streams, packets, messages, data items, and/ordata. For example, wireless communication units 112 and/or 142 mayinclude or may be implemented as part of a wireless Network InterfaceCard (NIC), and the like.

In some demonstrative embodiments, wireless communication medium 103 mayinclude a wireless P2P link. For example, devices 120 and/or 140 mayperform the functionality of a P2P client or a P2P group owner (GO).

In some demonstrative embodiments, wireless communication medium 103 mayinclude a WiFi direct link.

In some demonstrative embodiments, wireless communication medium 103 mayinclude any other suitable link.

In some demonstrative embodiments, devices 120 and/or 140 may beconfigured to provide one or more services to one or more remotedevices. For example, device 120 may be configured to provide printingservices, display services, Internet access services and/or any otherservices to device 140.

In some demonstrative embodiments, devices 120 and/or 140 may beconfigured to advertize the one or more services, for example, to enablethe remote devices to find the services. For example, device 120 may beconfigured to advertise one or more of the services provided by device120 to enable device 140 to discover the services provided by device120.

In some demonstrative embodiments, devices 120 and/or 140 may beconfigured to utilize the one or more services from the remote devices.For example, device 140 may be configured to utilize the services fromdevice 120.

In some demonstrative embodiments, devices 120 and/or 140 may beconfigured to connect to a device to receive the service provided by thedevice. For example, device 140 may be configured to connect to device120 to receive the services provided by device 120.

In some demonstrative embodiments, devices 120 and 140 may establish aP2P connection between devices 120 and 140 over wireless communicationmedium 103 to connect between devices 120 and 140, and to provide theone or more services between devices 120 and 140.

In some demonstrative embodiments, devices 120 and 140 may establish anyother connection between devices 120 and 140 over wireless communicationmedium 103.

In some demonstrative embodiments, devices 120 and/or 140 may include anApplication Service Platform (ASP) configured to manage the procedure ofreceiving and/or providing the one or more services, e.g., according toa predefined protocol.

In some demonstrative embodiments, device 120 may include an ASP 124,and/or device 140 may include an ASP 144, configured to manage anASP-session between devices 120 and 140.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may include asoftware module and/or a library module that implements functionsrequired for managing the procedure of receiving and/or providing theone or more services. For example, the functions may include discoveryof a service, session management, connection topology management,security management and/or any other function to support management ofthe services. In other embodiments, ASP 124 and/or ASP 144 may beimplemented using any other module and/or configuration.

In some demonstrative embodiments, ASP 124 and ASP 144 may be configuredto establish one or more ASP-sessions between devices 120 and 140 overthe P2P connection. The ASP-session may be utilized, for example, toprovide the one or more services between devices 120 and 140.

In some demonstrative embodiments, an ASP-session may include a logicallink between ASP 124 and 144, e.g., over the P2P connection betweendevices 120 and 140. The ASP-session may be configured, for example, tomanage the procedure of providing a service between devices 120 and 140.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may not beable to establish the one or more ASP-sessions, for example, if devices120 and/or 140 do not establish the P2P connection between devices 120and/or 140, e.g., prior to establishing the ASP-sessions.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may not beable to establish the one or more ASP-sessions over the P2P connection,for example, if devices 120 and 140 are not part of an ASP-P2P group.

In some demonstrative embodiments, ASP 124 and/or 144 may setup anASP-P2P group between ASP 124 and ASP 144 to establish the ASP-sessionand/or the P2P connection between ASP 124 and 144.

In some demonstrative embodiments, the ASP-P2P group may include a groupformed by an ASP, e.g., ASP 124 and/or 144, and may include a set ofdevices including a P2P group owner (GO) and zero or more clients. Forexample, the ASP-P2P group may include one of devices 120 and 140, e.g.,device 120, to perform the functionality of the GO, and another one ofdevices 120 and 140, e.g., device 140, to perform the functionality ofthe client.

In some demonstrative embodiments, establishing the ASP-session betweendevices of the ASP-P2P group may require users of the devices to performa provisioning procedure. For example, the users of the one or moredevices of the ASP-P2P group may perform the provisioning procedure, forexample, to assure that the correct devices are forming the ASP-P2Pgroup.

In one example, the devices may utilize a WiFi simple configuration(WSC) procedure to perform the provisioning procedure.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may form oneor more ASP-P2P groups based on one or more requests to establish one ormore ASP-sessions.

In one example, ASP 124 and/or ASP 144 may establish the one or moreASP-sessions between devices 120 and 140 to provide one or more servicesbetween devices 120 and 140.

In some demonstrative embodiments, ASP 124 and ASP 144 may exchangecredentials, e.g., during a provisioning phase.

In some demonstrative embodiments, the credentials may includeinformation, which may be required to join an ASP-P2P group. Forexample, the credentials may include a data structure, which may enablegaining access to the ASP-P2P group. In one example, the credentials mayinclude, for example, a WiFi Protected Access (WPA) personal pre-sharedkey (PSK). In other embodiments, the credentials may include any otherdata and/or information.

In some demonstrative embodiments, a persistent group may be a P2P groupbetween a first and second devices in which credentials are stored bythe first and/or the second devices and may be made available for reuseafter an initial use, e.g., of an ASP-session. The persistent group mayhave a lifetime, which may extend over a number of distinct ASP-sessionsafter the initial use until the persistent group is deliberatelydissolved, e.g., by ASP 124 and/or 144.

In some demonstrative embodiments, the users of the one more devices 120and/or 140 may be required to repeatedly perform the provisioningprocedure for each ASP-session between devices 120 and 140, for example,if the ASP-P2P group is not formed as an ASP-P2P persistent group. Thisrepeated provisioning may be inconvenient and/or may reduce userexperience.

In some demonstrative embodiments, an ASP-P2P group may always be formedas an ASP-P2P persistent group, e.g., as described below.

In some demonstrative embodiments, forming the ASP-P2P group as anASP-P2P persistent group may obviate the provisioning procedure forestablishing another ASP-session between devices of the ASP-P2Ppersistent group, for example, after forming the ASP-P2P persistentgroup, e.g., as described below.

In some demonstrative embodiments, ASP 124 may communicate with ASP 144to setup one or more ASP-P2P groups over wireless communication link103.

In some demonstrative embodiments, ASP 124 may form each ASP-P2P grouponly as an ASP-P2P persistent group 130 extendable over a plurality ofdistinct ASP-sessions.

In some demonstrative embodiments, ASP 124 may autonomously startASP-P2P persistent group 130 as a group owner (GO).

In some demonstrative embodiments, ASP 124 and/or 124 may setup ASP-P2Ppersistent group 130 as part of GO negotiation between ASP 124 and 144.

In some demonstrative embodiments, ASP 124 may communicate with ASP 144a P2P capability attribute including a group capability map.

In some demonstrative embodiments, the group capability map may includea persistent group bit always set to indicate that the ASP-P2P group isto be formed as ASP-P2P persistent group 130.

In one example, a persistent P2P group bit may always be set to apredefined value, e.g., “1”, to indicate the ASP-P2P group is an ASP-P2Ppersistent group. For example, a P2P capability attribute may becommunicated during a group formation procedure. The P2P capabilityattribute may include a group capability bitmap field including thepersistent P2P group bit set to the predefined value.

In some demonstrative embodiments, ASP 124 may store credentials 126 ofASP-P2P persistent group 130 for use during one or more additionalASP-sessions, e.g., subsequent to an ASP-session formed when setting upASP-P2P persistent group 130.

In some demonstrative embodiments, ASP 124 may store credentials 126 inmemory 129 and/or storage 195.

In some demonstrative embodiments, ASP 144 may store credentials 146 ofASP-P2P persistent group 130 for use during the ASP-sessions.

In some demonstrative embodiments, ASP 144 may store credentials 146 inmemory 129 and/or storage 195.

In some demonstrative embodiments, ASP 124 may assign a group identifierto identify ASP-P2P persistent group 130.

In some demonstrative embodiments, a different group identifier may beused for identifying different ASP-P2P persistent groups.

In some demonstrative embodiments, the group identifier of ASP-P2Ppersistent group 130 may not be changed and/or may remain the sameduring a lifetime of ASP-P2P persistent group 130.

In some demonstrative embodiments, ASP 124 may store, e.g., in storage195, the group identifier of ASP-P2P persistent group 130 in associationwith credentials 126 of ASP-P2P persistent group 130.

In some demonstrative embodiments, ASP 144 may store, e.g., in storage195, the group identifier of ASP-P2P persistent group 130 in associationwith credentials 146 of ASP-P2P persistent group 130.

In some demonstrative embodiments, storing credentials 126 and/or 146 inassociation with the group identifier of ASP-P2P persistent group 130may enable ASP 124 and/or 144 to invoke ASP-P2P persistent group 130 forthe one or more additional sessions, e.g., as described below.

In some demonstrative embodiments, ASP 124 may communicate with ASP 144to setup the P2P connection for an ASP-session 114 using credentials 126and/or 146 of ASP-P2P persistent group 130.

In some demonstrative embodiments, ASP 124 may communicate with ASP 144a provision discovery request 147 and a provision discovery response 127to setup ASP session 114. Provision discovery response 127 may be inresponse to provision discovery request 147.

In some demonstrative embodiments, ASP 144 may transmit provisiondiscovery request 147.

In some demonstrative embodiments, provision discovery request 147 mayinclude an indication of an intent to use ASP-P2P persistent group 130.

In some demonstrative embodiments, provision discovery request 147 mayinclude the group identifier of ASP-P2P persistent group 130, e.g., toidentify the ASP-P2P persistent group, which ASP 144 intends to use.

In some demonstrative embodiments, provision discovery request 147 mayindicate ASP 144 has credentials 146 available.

In some demonstrative embodiments, a P2P interface address may not bethe same for each ASP-session. For example, the P2P interface address ofASP-session 114 may be different from a P2P interface address ofanother, e.g., different, ASP-session.

In some demonstrative embodiments, the P2P interface address may be usedfor ASP 124 and/or ASP 144 to identify devices within ASP-P2P persistentgroup 130, e.g., devices 120 and/or 140.

In some demonstrative embodiments, provision discovery request 147and/or provision discovery response 127 may include the P2P interfaceaddress to be used be devices 120 and/or 140 during ASP-session 114.

In some demonstrative embodiments, an operating channel to communicateover the P2P connection may not be the same for each ASP-session. Forexample, the operating channel of ASP-session 114 may be different froman operating channel of another, e.g., different, ASP-session over theP2P connection.

In some demonstrative embodiments, provision discovery request 147and/or provision discovery response 127 may include the operatingchannel to be used within ASP-P2P persistent group 130. For example,provision discovery request 147 and/or provision discovery response 127may include an operating channel attribute, which may indicate theintended or the current operating channel of ASP-P2P persistent group130, in which devices, e.g., device 120 or 140, of ASP-P2P persistentgroup 130 may communicate.

In some demonstrative embodiments, ASP 124 may receive provisiondiscovery request 147 and may transmit provision discovery response 127to ASP 144, e.g., in response to provision discovery request 147.

In some demonstrative embodiments, provision discovery response 127 mayinclude an indication of a confirmation of ASP 124 to use ASP-P2Ppersistent group 130.

In some demonstrative embodiments, provision discovery response 127 mayindicate that ASP 124 has credentials 126 available.

In some demonstrative embodiments, ASP 124 may use, e.g., invoke,ASP-P2P persistent group 130 and may establish and/or open ASP-session114 utilizing the operating channel and the P2P interface addressindicated by provision discovery request 147, for example, upontransmitting the indication of confirmation, e.g., in provisiondiscovery response 127.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may form a newASP-P2P persistent group, for example, if ASP 124 does not havecredentials 126 available and/or if ASP 124 does not confirm to useASP-P2P persistent group 130.

In one example, provision discovery request 147 and/or provisiondiscovery response 127 may include a persistent P2P group invocationflag bit.

In some demonstrative embodiments, the persistent P2P group invocationflag bit in provision discovery request 147 may be set to a first value,e.g., “1”, for example, to indicate device 140 has credentials 146available and intends to invoke ASP-P2P persistent group 130.

In some demonstrative embodiments, the persistent P2P group invocationflag bit in provision discovery request 147 may be set to a secondvalue, e.g., “0”, for example, if device 140 does not have credentials146 available and/or if device 140 does not intend to invoke ASP-P2Ppersistent group 130.

In some demonstrative embodiments, the persistent P2P group invocationflag bit in provision discovery response 127 may be set to the firstvalue, e.g., “1”, for example, to indicate that device 120 hascredentials 126 available, and to confirm that ASP-P2P persistent group130 having the ASP-P2P group identifier, which was specified inprovision discovery request 147, will be invoked.

In some demonstrative embodiments, the persistent P2P group invocationflag bit in provision discovery response 127 may be set to the secondvalue, e.g., “0”, for example, if device 120 does not have credentials126 available and/or if ASP 124 does not intend to invoke ASP-P2Ppersistent group 130.

In some demonstrative embodiments, ASP 124 and 144 may perform the WSCprovisioning procedure, for example, if ASP 124 and/or ASP 144 intend toform a new ASP-P2P persistent group and/or if credentials 126 and/or 146are not available.

In some demonstrative embodiments, the persistent P2P group invocationflag bit may be part of a connection capability attribute, e.g., bit 3of a connection capability attribute of provision discovery request 147and/or provision discovery response 127. In other embodiments, thepersistent P2P group invocation flag bit may be part of a new attributeor an ASP extension attribute.

In one example, ASP 124 and ASP 144 may form ASP-P2P persistent group130 to establish an ASP-session to provide a printing service fromdevice 120 to device 140. ASP 124 may store credentials 126corresponding to the group identifier of ASP-P2P persistent group 130,and/or ASP 144 may store credentials 146 corresponding to the groupidentifier of ASP-P2P persistent group 130.

In some demonstrative embodiments, ASP 124 and/or ASP 144 may close theASP-session, for example, when device 140 completes utilizing theprinting service.

In some demonstrative embodiments, ASP 144 may request to open a new ASPsession, e.g., ASP-session 114, to utilize a display service from device120.

In some demonstrative embodiments, ASP 144 may transmit provisiondiscovery request 147 to open ASP-session 114. Provision discoveryrequest 147 may indicate the intent to use ASP-P2P persistent group 130for ASP-session 114.

In some demonstrative embodiments, ASP 124 may receive provisiondiscovery request 147, and may invoke ASP-P2P persistent group 130 toestablish ASP-session 114, e.g., utilizing credentials 126 and 146, toprovide the display service.

In some demonstrative embodiments, ASP 124 may be able to invoke ASP-P2Ppersistent group 130, for example, only if credentials 126 and/or 146are available.

In some demonstrative embodiments, ASP 124 and/or 144 may not need toperform the provisioning procedure, for example, upon invoking ASP-P2Ppersistent group 130, for example, since credentials 126 and/or 146 areavailable.

In some demonstrative embodiments, forming each ASP-P2P group as anASP-P2P persistent group, e.g., group 130, may eliminate theprovisioning procedure, which may reduce setup-time for establishing anadditional ASP session, e.g., ASP-session 114.

In some demonstrative embodiments, reducing the setup-time may increaseperformance and/or may reduce power consumption of devices 120 and/or140.

Reference is made to FIG. 2, which schematically illustrates a sequenceof operations between a first wireless communication device 240 and asecond wireless communication device 220, in accordance with somedemonstrative embodiments. For example, device 220 may perform thefunctionality of device 120 (FIG. 1) and/or device 240 may perform thefunctionality of device 140 (FIG. 1).

In some demonstrative embodiments, device 240 may request to open an ASPsession between devices 240 and 220, e.g., to provide a service fromdevice 220 to device 240.

As shown in FIG. 2, device 240 may transmit a P2P provision discoveryrequest message 247 to request to open the ASP session. For example,provision discovery message 247 may perform the functionality ofprovision discovery message 147 (FIG. 1).

As shown in FIG. 2, P2P provision discovery request message 247 mayinclude a session info field, a connection capability field, apersistent P2P group invocation field, and/or a P2P interface address.For example, the P2P group invocation field may include an indication ofan intent to use an ASP-P2P persistent group; the connection capabilityfield may include the persistent group bit set to one to indicate theASP-P2P group is to be formed as an ASP-P2P persistent group; and/or theP2P interface address field may include the P2P interface address of therequested ASP-session, e.g., as described above.

As shown in FIG. 2, device 240 may retransmit (242) provision discoveryrequest message 247, for example, if device 220 does not receiveprovision discovery message 247.

As shown in FIG. 2, device 220 may receive provision discovery requestmessage 247 and may transmit a provision discovery response message 227in response to provision discovery request message 247. For example,provision discovery response message 227 may perform the functionalityof provision discovery response message 127 (FIG. 1).

As shown in FIG. 2, provision discovery response message 227 may includea persistent P2P group invocation field, and/or a P2P interface address.For example, the P2P group invocation field may include the indicationof conformation to use the ASP-P2P persistent group, and/or the P2Pinterface address field may include the P2P interface address of therequested ASP-session, e.g., as described above.

As shown in FIG. 2, devices 220 and/or 240 may communicate additionalframes 250 between devices 220 and/or 240. For example, devices 220and/or 240 may communicate additional provision discovery request orresponse frames, a request session message and/or an added sessionmessage.

As shown in FIG. 2, devices 220 and/or 240 may communicate P2P-ASPmessages 254 between devices 220 and/or 240. For example, devices 220and/or 240 may communicate a request session message and/or an allowedport message.

Reference is made to FIG. 3, which schematically illustrates a flowchart of a method of setting up an ASP-P2P group, in accordance withsome demonstrative embodiments. For example, one or more of theoperations of the method of FIG. 3 may be performed by a wirelesscommunication system, e.g., system 100 (FIG. 1); a wirelesscommunication device, e.g., device 120 (FIG. 1) and/or device 140 (FIG.1); and/or an ASP, e.g., ASP 124 (FIG. 1), and/or ASP 144 (FIG. 1).

As indicated at block 302, the method may include setting up one or moreASP-P2P groups over a wireless communication link between a first ASPand a second ASP. For example, ASP 124 and ASP 144 (FIG. 1) may setupthe one or more ASP-P2P groups over WM 103 (FIG. 1) between ASP 124 and144 (FIG. 1), e.g., as described above.

As indicated at block 304, setting up the one or more ASP-P2P groups mayinclude forming each ASP-P2P group only as an ASP-P2P persistent groupextendable over a plurality of distinct ASP-sessions. For example, ASP124 (FIG. 1) may setup ASP-P2P persistent group 130 (FIG. 1) extendableover the plurality of distinct ASP-sessions, e.g., as described above.

As indicated at block 306, forming each ASP-P2P group only as theASP-P2P persistent group may include communicating a P2P capabilityattribute including a group capability map. The group capability map mayinclude a persistent group bit always set to indicate the ASP-P2P groupis to be formed as an ASP-P2P persistent group. For example, ASP 124(FIG. 1) and ASP 144 (FIG. 1) may communicate the P2P capabilityattribute including the persistent group bit set to one, e.g., asdescribed above.

As indicated at block 308, setting up the one or more ASP-P2P groups mayinclude storing at the first ASP credentials of the ASP-P2P persistentgroup for use during the ASP-sessions. For example, ASP 124 (FIG. 1) maystore credentials 126 (FIG. 1) for use during the ASP-sessions, e.g., asdescribed above.

As indicated at block 310, the method may include setting up a P2Pconnection for an ASP-session between the first ASP and the second ASP,the ASP-session using credentials of the ASP-P2P persistent group. Forexample, ASP 124 and ASP 144 (FIG. 1) may setup ASP session 114 (FIG. 1)using credentials 126 (FIG. 1) of ASP-P2P persistent group 130 (FIG. 1),e.g., as described above.

As indicated at block 312, setting up the P2P connection for anASP-session may include communicating a provision discovery request anda provision discovery response between the first and second ASPs. Theprovision discovery response may be in response to the provisiondiscovery request. For example, ASP 124 and ASP 144 (FIG. 1) maycommunicate provision discovery request 147 (FIG. 1) and provisiondiscovery response 127 (FIG. 1), e.g., as described above.

As indicated at block 314, communicating the provision discovery requestand the provision discovery response may include communicating anindication of an intent to use the ASP-P2P persistent group and anindication of a confirmation to use the ASP-P2P persistent group. Forexample, provision discovery request 147 (FIG. 1) may include anindication of the intention to use ASP-P2P persistent group 130 (FIG. 1)and/or provision discovery response 127 (FIG. 1) may include anindication of the confirmation to use ASP-P2P persistent group 130 (FIG.1), e.g., as described above.

As indicated at block 316, communicating the provision discovery requestand the provision discovery response may include communicating a P2Pinterface address to be used during the ASP-session. For example,provision discovery request 147 (FIG. 1) and/or provision discoveryresponse 127 (FIG. 1) may include the P2P interface address, e.g., asdescribed above.

Reference is made to FIG. 4, which schematically illustrates a productof manufacture 400, in accordance with some demonstrative embodiments.Product 400 may include a non-transitory machine-readable storage medium402 to store logic 404, which may be used, for example, to perform atleast part of the functionality of device 140 (FIG. 1), device 120 (FIG.1), ASP 124 (FIG. 1), ASP 144 (FIG. 1), and/or to perform one or moreoperations of the method of FIG. 3. The phrase “non-transitorymachine-readable medium” is directed to include all computer-readablemedia, with the sole exception being a transitory propagating signal.

In some demonstrative embodiments, product 400 and/or machine-readablestorage medium 402 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 402 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 404 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 404 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising a first Application ServicePlatform (ASP) to communicate with a second ASP to setup one or more ASPPeer-to-Peer (P2P) (ASP-P2P) groups over a wireless communication link,the first ASP is to form each ASP-P2P group only as an ASP-P2Ppersistent group extendable over a plurality of distinct sessions, thefirst ASP is to store credentials of the ASP-P2P persistent group foruse during the sessions.

Example 2 includes the subject matter of Example 1 and optionally,wherein the first ASP is to communicate with the second ASP a P2Pcapability attribute including a group capability map, the groupcapability map includes a persistent group bit always set to indicatethe ASP-P2P group is to be formed as the ASP-P2P persistent group.

Example 3 includes the subject matter of Example 1 or 2 and optionally,wherein the first ASP is to communicate with the second ASP a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, the provision discovery request includingan indication of an intent to use the ASP-P2P persistent group, and theprovision discovery response including an indication of a confirmationto use the ASP-P2P persistent group.

Example 4 includes the subject matter of Example 3 and optionally,wherein the first ASP is to transmit the provision discovery request andto receive the provision discovery response, the provision discoveryrequest to indicate the first ASP has the credentials available.

Example 5 includes the subject matter of Example 3 and optionally,wherein the first ASP is to receive the provision discovery request andto transmit the provision discovery response, the provision discoveryresponse to indicate the first ASP has the credentials available.

Example 6 includes the subject matter of any one of Examples 1-5 andoptionally, wherein the first ASP is to communicate with the second ASPa provision discovery request and a provision discovery response to setup an ASP-P2P session, the provision discovery response in response tothe provision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes a P2P interfaceaddress to be used within the ASP-P2P persistent group.

Example 7 includes the subject matter of any one of Examples 1-6 andoptionally, wherein the first ASP is to communicate with the second ASPa provision discovery request and a provision discovery response to setup an ASP-P2P session, the provision discovery response in response tothe provision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes an operatingchannel to be used within the ASP-P2P persistent group.

Example 8 includes the subject matter of any one of Examples 1-7 andoptionally, wherein the first ASP is to autonomously start the ASP-P2Ppersistent group as a group owner.

Example 9 includes the subject matter of any one of Examples 1-8 andoptionally, wherein the wireless communication link comprises aWireless-Fidelity (WiFi) Direct link.

Example 10 includes an apparatus comprising a first Application ServicePlatform (ASP) to communicate with a second ASP to setup a Peer-to-Peer(P2P) connection for an ASP-session using credentials of an ASP-P2Ppersistent group, the first ASP is to communicate with the second ASP aprovision discovery request and a provision discovery response to set upthe ASP session, the provision discovery response in response to theprovision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes a P2P interfaceaddress to be used during the session.

Example 11 includes the subject matter of Example 10 and optionally,wherein each of the provision discovery request and the provisiondiscovery response includes an operating channel to be used within theASP-P2P persistent group.

Example 12 includes the subject matter of Example 10 or 11 andoptionally, wherein the first ASP is to communicate with the second ASPa P2P capability attribute including a group capability map, the groupcapability map includes a persistent group bit set to indicate theASP-P2P persistent group.

Example 13 includes the subject matter of any one of Examples 10-12 andoptionally, wherein the provision discovery request includes anindication of an intent to use the ASP-P2P persistent group, and theprovision discovery response includes an indication of a confirmation touse the ASP-P2P persistent group.

Example 14 includes the subject matter of any one of Examples 10-13 andoptionally, wherein the first ASP is to transmit the provision discoveryrequest and to receive the provision discovery response, the provisiondiscovery request to indicate the first ASP has the credentialsavailable.

Example 15 includes the subject matter of any one of Examples 10-13 andoptionally, wherein the first ASP is to receive the provision discoveryrequest and to transmit the provision discovery response, the provisiondiscovery response to indicate the first ASP has the credentialsavailable.

Example 16 includes the subject matter of any one of Examples 10-15 andoptionally, wherein the first ASP is to autonomously start the ASP-P2Ppersistent group as a group owner.

Example 17 includes the subject matter of any one of Examples 10-16 andoptionally, wherein the ASP-session comprises a session over aWireless-Fidelity (WiFi) Direct link.

Example 18 includes a system comprising a first wireless communicationdevice including a wireless communication unit to communicate with asecond wireless communication device over a wireless communication link;and a first Application Service Platform (ASP) to communicate with asecond ASP of the second wireless communication device to setup one ormore ASP Peer-to-Peer (P2P) (ASP-P2P) groups over the wirelesscommunication link, the first ASP is to form each ASP-P2P group only asan ASP-P2P persistent group extendable over a plurality of distinctsessions, the first ASP is to store credentials of the ASP-P2Ppersistent group for use during the sessions.

Example 19 includes the subject matter of Example 18 and optionally,wherein the first ASP is to communicate with the second ASP a P2Pcapability attribute including a group capability map, the groupcapability map includes a persistent group bit always set to indicatethe ASP-P2P group is to be formed as the ASP-P2P persistent group.

Example 20 includes the subject matter of Example 18 or 19 andoptionally, wherein the first ASP is to communicate with the second ASPa provision discovery request and a provision discovery response to setup an ASP-P2P session, the provision discovery response in response tothe provision discovery request, the provision discovery requestincluding an indication of an intent to use the ASP-P2P persistentgroup, and the provision discovery response including an indication of aconfirmation to use the ASP-P2P persistent group.

Example 21 includes the subject matter of Example 20 and optionally,wherein the first ASP is to transmit the provision discovery request andto receive the provision discovery response, the provision discoveryrequest to indicate the first ASP has the credentials available.

Example 22 includes the subject matter of Example 20 and optionally,wherein the first ASP is to receive the provision discovery request andto transmit the provision discovery response, the provision discoveryresponse to indicate the first ASP has the credentials available.

Example 23 includes the subject matter of any one of Examples 18-22 andoptionally, wherein the first ASP is to communicate with the second ASPa provision discovery request and a provision discovery response to setup an ASP-P2P session, the provision discovery response in response tothe provision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes a P2P interfaceaddress to be used within the ASP-P2P persistent group.

Example 24 includes the subject matter of any one of Examples 18-23 andoptionally, wherein the first ASP is to communicate with the second ASPa provision discovery request and a provision discovery response to setup an ASP-P2P session, the provision discovery response in response tothe provision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes an operatingchannel to be used within the ASP-P2P persistent group.

Example 25 includes the subject matter of any one of Examples 18-24 andoptionally, wherein the first ASP is to autonomously start the ASP-P2Ppersistent group as a group owner.

Example 26 includes the subject matter of any one of Examples 18-25 andoptionally, wherein the wireless communication link comprises aWireless-Fidelity (WiFi) Direct link.

Example 27 includes a system comprising a first wireless communicationdevice including a wireless communication unit to communicate with asecond wireless communication device over a wireless communication link;and a first Application Service Platform (ASP) to communicate with asecond ASP of the second wireless communication device to setup aPeer-to-Peer (P2P) connection for an ASP-session using credentials of anASP-P2P persistent group, the first ASP is to communicate with thesecond ASP a provision discovery request and a provision discoveryresponse to set up the ASP session, the provision discovery response inresponse to the provision discovery request, wherein each of theprovision discovery request and the provision discovery responseincludes a P2P interface address to be used during the session.

Example 28 includes the subject matter of Example 27 and optionally,wherein each of the provision discovery request and the provisiondiscovery response includes an operating channel to be used within theASP-P2P persistent group.

Example 29 includes the subject matter of Example 27 or 28 andoptionally, wherein the first ASP is to communicate with the second ASPa P2P capability attribute including a group capability map, the groupcapability map includes a persistent group bit set to indicate theASP-P2P persistent group.

Example 30 includes the subject matter of any one of Examples 27-29 andoptionally, wherein the provision discovery request includes anindication of an intent to use the ASP-P2P persistent group, and theprovision discovery response includes an indication of a confirmation touse the ASP-P2P persistent group.

Example 31 includes the subject matter of any one of Examples 27-30 andoptionally, wherein the first ASP is to transmit the provision discoveryrequest and to receive the provision discovery response, the provisiondiscovery request to indicate the first ASP has the credentialsavailable.

Example 32 includes the subject matter of any one of Examples 27-30 andoptionally, wherein the first ASP is to receive the provision discoveryrequest and to transmit the provision discovery response, the provisiondiscovery response to indicate the first ASP has the credentialsavailable.

Example 33 includes the subject matter of any one of Examples 27-32 andoptionally, wherein the first ASP is to autonomously start the ASP-P2Ppersistent group as a group owner.

Example 34 includes the subject matter of any one of Examples 27-33 andoptionally, wherein the ASP-session comprises a session over aWireless-Fidelity (WiFi) Direct link.

Example 35 includes a method comprising setting up one or moreApplication Service Platform (ASP) Peer-to-Peer (P2P) (ASP-P2P) groupsover a wireless communication link between a first ASP and a second ASP,the setting up including forming each ASP-P2P group only as an ASP-P2Ppersistent group extendable over a plurality of distinct sessions; andstoring at the first ASP credentials of the ASP-P2P persistent group foruse during the sessions.

Example 36 includes the subject matter of Example 35 and optionally,comprising communicating with the second ASP a P2P capability attributeincluding a group capability map, the group capability map includes apersistent group bit always set to indicate the ASP-P2P group is to beformed as the ASP-P2P persistent group.

Example 37 includes the subject matter of Example 35 or 36 andoptionally, comprising communicating with the second ASP a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, the provision discovery request includingan indication of an intent to use the ASP-P2P persistent group, and theprovision discovery response including an indication of a confirmationto use the ASP-P2P persistent group.

Example 38 includes the subject matter of Example 37 and optionally,comprising transmitting the provision discovery request and receivingthe provision discovery response, the provision discovery request toindicate the first ASP has the credentials available.

Example 39 includes the subject matter of Example 37 and optionally,comprising receiving the provision discovery request and transmittingthe provision discovery response, the provision discovery response toindicate the first ASP has the credentials available.

Example 40 includes the subject matter of any one of Examples 35-39 andoptionally, comprising communicating with the second ASP a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes a P2P interfaceaddress to be used within the ASP-P2P persistent group.

Example 41 includes the subject matter of any one of Examples 35-40 andoptionally, comprising communicating with the second ASP a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes an operatingchannel to be used within the ASP-P2P persistent group.

Example 42 includes the subject matter of any one of Examples 35-41 andoptionally, comprising autonomously starting the ASP-P2P persistentgroup as a group owner.

Example 43 includes the subject matter of any one of Examples 35-42 andoptionally, wherein the wireless communication link comprises aWireless-Fidelity (WiFi) Direct link.

Example 44 includes a method comprising setting up one a Peer-to-Peer(P2P) connection for an ASP-session between a first Application ServicePlatform (ASP) and a second ASP, the ASP-session using credentials of anASP-P2P persistent group, the setting up including communicating aprovision discovery request and a provision discovery response betweenthe first and second ASPs, the provision discovery response in responseto the provision discovery request, wherein each of the provisiondiscovery request and the provision discovery response includes a P2Pinterface address to be used during the session.

Example 45 includes the subject matter of Example 44 and optionally,wherein each of the provision discovery request and the provisiondiscovery response includes an operating channel to be used within theASP-P2P persistent group.

Example 46 includes the subject matter of Example 44 or 45 andoptionally, comprising communicating a P2P capability attributeincluding a group capability map, the group capability map includes apersistent group bit set to indicate the ASP-P2P persistent group.

Example 47 includes the subject matter of any one of Examples 44-46 andoptionally, wherein the provision discovery request includes anindication of an intent to use the ASP-P2P persistent group, and theprovision discovery response includes an indication of a confirmation touse the ASP-P2P persistent group.

Example 48 includes the subject matter of any one of Examples 44-47 andoptionally, comprising transmitting the provision discovery request andreceiving the provision discovery response, the provision discoveryrequest to indicate the first ASP has the credentials available.

Example 49 includes the subject matter of any one of Examples 44-47 andoptionally, comprising receiving the provision discovery request andtransmitting the provision discovery response, the provision discoveryresponse to indicate the first ASP has the credentials available.

Example 50 includes the subject matter of any one of Examples 44-49 andoptionally, comprising autonomously starting the ASP-P2P persistentgroup as a group owner.

Example 51 includes the subject matter of any one of Examples 44-50 andoptionally, wherein the ASP-session comprises a session over aWireless-Fidelity (WiFi) Direct link.

Example 52 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in setting up one or more ASP Peer-to-Peer (P2P) (ASP-P2P) groupsover a wireless communication link between a first Application ServicePlatform (ASP) and a second ASP, the setting up including forming eachASP-P2P group only as an ASP-P2P persistent group extendable over aplurality of distinct sessions; and storing at the first ASP credentialsof the ASP-P2P persistent group for use during the sessions.

Example 53 includes the subject matter of Example 52 and optionally,wherein the instructions result in communicating a P2P capabilityattribute including a group capability map, the group capability mapincludes a persistent group bit always set to indicate the ASP-P2P groupis to be formed as the ASP-P2P persistent group.

Example 54 includes the subject matter of Example 52 or 53 andoptionally, wherein the instructions result in communicating with thesecond ASP a provision discovery request and a provision discoveryresponse to set up an ASP-P2P session, the provision discovery responsein response to the provision discovery request, the provision discoveryrequest including an indication of an intent to use the ASP-P2Ppersistent group, and the provision discovery response including anindication of a confirmation to use the ASP-P2P persistent group.

Example 55 includes the subject matter of Example 54 and optionally,wherein the instructions result in transmitting the provision discoveryrequest and receiving the provision discovery response, the provisiondiscovery request to indicate the first ASP has the credentialsavailable.

Example 56 includes the subject matter of Example 54 and optionally,wherein the instructions result in receiving the provision discoveryrequest and transmitting the provision discovery response, the provisiondiscovery response to indicate the first ASP has the credentialsavailable.

Example 57 includes the subject matter of any one of Examples 52-56 andoptionally, wherein the instructions result in communicating a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes a P2P interfaceaddress to be used within the ASP-P2P persistent group.

Example 58 includes the subject matter of any one of Examples 52-57 andoptionally, wherein the instructions result in communicating a provisiondiscovery request and a provision discovery response to set up anASP-P2P session, the provision discovery response in response to theprovision discovery request, wherein each of the provision discoveryrequest and the provision discovery response includes an operatingchannel to be used within the ASP-P2P persistent group.

Example 59 includes the subject matter of any one of Examples 52-58 andoptionally, wherein the instructions result in autonomously starting theASP-P2P persistent group as a group owner.

Example 60 includes the subject matter of any one of Examples 52-59 andoptionally, wherein the wireless communication link comprises aWireless-Fidelity (WiFi) Direct link.

Example 61 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in setting up one a Peer-to-Peer (P2P) connection for anASP-session between a first Application Service Platform (ASP) and asecond ASP, the ASP-session using credentials of an ASP-P2P persistentgroup, the setting up including communicating a provision discoveryrequest and a provision discovery response between the first and secondASPs, the provision discovery response in response to the provisiondiscovery request, wherein each of the provision discovery request andthe provision discovery response includes a P2P interface address to beused during the session.

Example 62 includes the subject matter of Example 61 and optionally,wherein each of the provision discovery request and the provisiondiscovery response includes an operating channel to be used within theASP-P2P persistent group.

Example 63 includes the subject matter of Example 61 or 62 andoptionally, wherein the instructions result in communicating a P2Pcapability attribute including a group capability map, the groupcapability map includes a persistent group bit set to indicate theASP-P2P persistent group.

Example 64 includes the subject matter of any one of Examples 61-63 andoptionally, wherein the provision discovery request includes anindication of an intent to use the ASP-P2P persistent group, and theprovision discovery response includes an indication of a confirmation touse the ASP-P2P persistent group.

Example 65 includes the subject matter of any one of Examples 61-64 andoptionally, wherein the instructions result in transmitting theprovision discovery request and receiving the provision discoveryresponse, the provision discovery request to indicate the first ASP hasthe credentials available.

Example 66 includes the subject matter of any one of Examples 61-64 andoptionally, wherein the instructions result in receiving the provisiondiscovery request and transmitting the provision discovery response, theprovision discovery response to indicate the first ASP has thecredentials available.

Example 67 includes the subject matter of any one of Examples 61-66 andoptionally, wherein the instructions result in autonomously starting theASP-P2P persistent group as a group owner.

Example 68 includes the subject matter of any one of Examples 61-67 andoptionally, wherein the ASP-session comprises a session over aWireless-Fidelity (WiFi) Direct link.

Example 69 includes an apparatus comprising means for setting up one ormore ASP Peer-to-Peer (P2P) (ASP-P2P) groups over a wirelesscommunication link between a first Application Service Platform (ASP)and a second ASP, the setting up including forming each ASP-P2P grouponly as an ASP-P2P persistent group extendable over a plurality ofdistinct sessions; and means for storing at the first ASP credentials ofthe ASP-P2P persistent group for use during the sessions.

Example 70 includes the subject matter of Example 69 and optionally,comprising means for communicating a P2P capability attribute includinga group capability map, the group capability map includes a persistentgroup bit always set to indicate the ASP-P2P group is to be formed asthe ASP-P2P persistent group.

Example 71 includes the subject matter of Example 69 or 70 andoptionally, comprising means for communicating a provision discoveryrequest and a provision discovery response to set up an ASP-P2P session,the provision discovery response in response to the provision discoveryrequest, the provision discovery request including an indication of anintent to use the ASP-P2P persistent group, and the provision discoveryresponse including an indication of a confirmation to use the ASP-P2Ppersistent group.

Example 72 includes the subject matter of Example 71 and optionally,comprising means for transmitting the provision discovery request andmeans for receiving the provision discovery response, the provisiondiscovery request to indicate the first ASP has the credentialsavailable.

Example 73 includes the subject matter of Example 71 and optionally,comprising means for receiving the provision discovery request andtransmitting the provision discovery response, the provision discoveryresponse to indicate the first ASP has the credentials available.

Example 74 includes the subject matter of any one of Examples 69-73 andoptionally, comprising means for communicating a provision discoveryrequest and a provision discovery response to set up an ASP-P2P session,the provision discovery response in response to the provision discoveryrequest, wherein each of the provision discovery request and theprovision discovery response includes a P2P interface address to be usedwithin the ASP-P2P persistent group.

Example 75 includes the subject matter of any one of Examples 69-74 andoptionally, comprising means for communicating a provision discoveryrequest and a provision discovery response to set up an ASP-P2P session,the provision discovery response in response to the provision discoveryrequest, wherein each of the provision discovery request and theprovision discovery response includes an operating channel to be usedwithin the ASP-P2P persistent group.

Example 76 includes the subject matter of any one of Examples 69-75 andoptionally, comprising means for autonomously starting the ASP-P2Ppersistent group as a group owner.

Example 77 includes the subject matter of any one of Examples 69-76 andoptionally, wherein the wireless communication link comprises aWireless-Fidelity (WiFi) Direct link.

Example 78 includes an apparatus comprising means for setting up one aPeer-to-Peer (P2P) connection for an ASP-session between a firstApplication Service Platform (ASP) and a second ASP, the ASP-sessionusing credentials of an ASP-P2P persistent group, the means for settingup including means for communicating a provision discovery request and aprovision discovery response between the first and second ASPs, theprovision discovery response in response to the provision discoveryrequest, wherein each of the provision discovery request and theprovision discovery response includes a P2P interface address to be usedduring the session.

Example 79 includes the subject matter of Example 78 and optionally,wherein each of the provision discovery request and the provisiondiscovery response includes an operating channel to be used within theASP-P2P persistent group.

Example 80 includes the subject matter of Example 78 or 79 andoptionally, comprising means for communicating a P2P capabilityattribute including a group capability map, the group capability mapincludes a persistent group bit set to indicate the ASP-P2P persistentgroup.

Example 81 includes the subject matter of any one of Examples 78-80 andoptionally, wherein the provision discovery request includes anindication of an intent to use the ASP-P2P persistent group, and theprovision discovery response includes an indication of a confirmation touse the ASP-P2P persistent group.

Example 82 includes the subject matter of any one of Examples 78-81 andoptionally, comprising means for transmitting the provision discoveryrequest and means for receiving the provision discovery response, theprovision discovery request to indicate the first ASP has thecredentials available.

Example 83 includes the subject matter of any one of Examples 78-81 andoptionally, comprising means for receiving the provision discoveryrequest and means for transmitting the provision discovery response, theprovision discovery response to indicate the first ASP has thecredentials available.

Example 84 includes the subject matter of any one of Examples 78-83 andoptionally, comprising means for autonomously starting the ASP-P2Ppersistent group as a group owner.

Example 85 includes the subject matter of any one of Examples 78-84 andoptionally, wherein the ASP-session comprises a session over aWireless-Fidelity (WiFi) Direct link.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents may occur to those skilled in the art. It is, therefore, tobe understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theinvention.

What is claimed is:
 1. A first wireless device comprising: a radio; atleast one processor; and at least one non-transitory storage medium tostore logic configured to, when executed by said processor, cause afirst Application Service Platform (ASP) on said first wireless deviceto: set up at least one ASP Peer-to-Peer (P2P) (ASP-P2P) group betweensaid first ASP and a second ASP of a second wireless device, the ASP-P2Pgroup to always be formed as a persistent P2P group extendable over aplurality of distinct sessions; and when a group formation procedure ofthe ASP-P2P group is to be performed, set a persistent P2P group bit ofa group capability map in a P2P capability attribute only to a value ofone to indicate that the ASP-P2P group is to be formed as a persistentP2P group.
 2. The first wireless device of claim 1, wherein the logic,when executed by said processor, is to cause said first ASP to storecredentials of said ASAP-P2P group.
 3. The first wireless device ofclaim 1, wherein the logic, when executed by said processor, is to causethe first ASP to send a provision discovery request comprising anindication of an intent to use said ASP-P2P persistent group.
 4. Thefirst wireless device of claim 1, wherein the logic, when executed bysaid processor, is to cause the first ASP to process a receivedprovision discovery response comprising an indication of a confirmationto use said ASP-P2P persistent group.
 5. The first wireless device ofclaim 1, wherein the logic, when executed by said processor, is to causethe first ASP to process a received provision discovery requestcomprising an indication of an intent to use said ASP-P2P persistentgroup.
 6. The first wireless device of claim 1, wherein the logic, whenexecuted by said processor, is to cause the first ASP to send aprovision discovery response comprising an indication of a confirmationto use said ASP-P2P persistent group.
 7. The first wireless device ofclaim 1, wherein the logic, when executed by said processor, is to causethe first ASP to send a provision discovery message comprising a P2Pinterface address, and an operating channel to be used by the ASP-P2Pgroup.
 8. The first wireless device of claim 1, wherein the logic, whenexecuted by said processor, is to cause the first ASP to autonomouslystart said ASP-P2P persistent group as a group owner (GO).
 9. The firstwireless device of claim 1 comprising one or more antennas.
 10. Thefirst wireless device of claim 1 being a mobile device.
 11. A productcomprising one or more tangible computer-readable non-transitory storagemedia comprising computer-executable instructions operable to, whenexecuted by at least one computer processor, enable the at least onecomputer processor to implement one or more operations at a firstApplication Service Platform (ASP) on a first wireless device, theoperations comprising: setting up at least one ASP Peer-to-Peer (P2P)(ASP-P2P) group between said first ASP and a second ASP of a secondwireless device, the ASP-P2P group to always be formed as a persistentP2P group extendable over a plurality of distinct sessions; and when agroup formation procedure of the ASP-P2P group is to be performed,setting a persistent P2P group bit of a group capability map in a P2Pcapability attribute only to a value of one to indicate that the ASP-P2Pgroup is to be formed as a persistent P2P group.
 12. The product ofclaim 11, wherein the operations comprise storing credentials of saidASAP-P2P group.
 13. The product of claim 11, wherein the operationscomprise sending a provision discovery request comprising an indicationof an intent to use said ASP-P2P persistent group.
 14. The product ofclaim 11, wherein the operations comprise processing a receivedprovision discovery response comprising an indication of a confirmationto use said ASP-P2P persistent group.
 15. The product of claim 11,wherein the operations comprise processing a received provisiondiscovery request comprising an indication of an intent to use saidASP-P2P persistent group.
 16. The product of claim 11, wherein theoperations comprise sending a provision discovery response comprising anindication of a confirmation to use said ASP-P2P persistent group. 17.The product of claim 11, wherein the operations comprise sending aprovision discovery message comprising a P2P interface address, and anoperating channel to be used by the ASP-P2P group.
 18. The product ofclaim 11, wherein the operations comprise autonomously starting saidASP-P2P persistent group as a group owner (GO).
 19. A method to beperformed by a first Application Service Platform (ASP) on a firstwireless device, the method comprising: setting up at least one ASPPeer-to-Peer (P2P) (ASP-P2P) group between said first ASP and a secondASP of a second wireless device, the ASP-P2P group to always be formedas a persistent P2P group extendable over a plurality of distinctsessions; and when a group formation procedure of the ASP-P2P group isto be performed, setting a persistent P2P group bit of a groupcapability map in a P2P capability attribute only to a value of one toindicate that the ASP-P2P group is to be formed as a persistent P2Pgroup.
 20. The method of claim 19 comprising storing credentials of saidASAP-P2P group.
 21. The method of claim 19 comprising sending aprovision discovery request comprising an indication of an intent to usesaid ASP-P2P persistent group.
 22. The method of claim 19 comprisingprocessing a received provision discovery response comprising anindication of a confirmation to use said ASP-P2P persistent group. 23.The method of claim 19 comprising processing a received provisiondiscovery request comprising an indication of an intent to use saidASP-P2P persistent group.
 24. The method of claim 19 comprising sendinga provision discovery response comprising an indication of aconfirmation to use said ASP-P2P persistent group.
 25. The method ofclaim 19 comprising sending a provision discovery message comprising aP2P interface address, and an operating channel to be used by theASP-P2P group.
 26. The method of claim 19 comprising autonomouslystarting said ASP-P2P persistent group as a group owner (GO).